| From: | Sam Jordan |
| Date: | 06 Apr 00 at 17:15:37 |
| Subject: | Re: Odp: Re: PPC Crashes when Multitasking |
Am 06-Apr-00 schrieb Bo Simmons:
>Hi Mark
>What is in fact the stack?
>If it is only reserving memory, then why don't the programmers make their
>programs in a ways they reserver the mem on their own?
It's a design question. So if anyone writes a new program and does
a proper design, then no such problems will ever occur. In case that
someone has to work with an existing software he is more or less stuck
to work with the design of that software, which might heavily rely on
local variables/arrays. Of course you can easily say that an existing
software can be changed, but it's a lot of work and it's something quite
dangerous to do, because lots of new errors might be introduced, especially
when we are talking about ports of big and complex software, where the
porters have in no way the same knowledge about the inner workings
of the software compared to the original developers.
Of course there is quite an easy way to solve the stack problem even
for ports: change the stack using exec/StackSwap. For PPC programs
this can also be done by providing a small 68k startup code that
changes the stack and then jumps into the PPC main function. The
PPC stack size is derived from the 68K stack size. WarpOS right now
doubles the size and defines a minimal value, too.
bye